SUPPORT / SAMPLES & SAS NOTES
 

Support

Problem Note 53020: Errors occur when you try to invoke SAS® Forecast Studio or SAS® Time Series Studio with Java 1.7.0_51 or higher

DetailsHotfixAboutRate It

The SAS Forecast Studio and SAS Time Series Studio Java Web Start client applications do not work with Java update 1.7.0_51 or higher. When you try to invoke these applications, you receive the following error:

error message

On the Exceptions tab in the dialog box, the Java exception details contain a large number of missing Permissions and Codebase manifest attributes, as shown below:

Missing Permissions manifest attribute for: ........./SASForecastServer/sas.timeseries.commons.core.jar
Missing Codebase manifest attribute for: ........./SASForecastServer/sas.timeseries.commons.core.jar
Missing Permissions manifest attribute for: ........./SASForecastServer/sas.forecasting.swing.jar
Missing Codebase manifest attribute for: ........./SASForecastServer/sas.forecasting.swing.jar
Missing Permissions manifest attribute for: ........./SASForecastServer/sas.forecasting.client.jar
Missing Codebase manifest attribute for: ........./SASForecastServer/sas.forecasting.client.jar
Missing Permissions manifest attribute for: ........./SASForecastServer/log4j.jar
Missing Codebase manifest attribute for: ........./SASForecastServer/log4j.jar
Missing Permissions manifest attribute for: ........./SASForecastServer/sas.swing.login.jar
Missing Codebase manifest attribute for: ........./SASForecastServer/sas.swing.login.jar

The latest version of Java requires the Permissions attribute to be present in all JAR files that are used in Java Web Start or that are used as applets.

Currently, there is no workaround or solution for this problem.

Click the Hot Fix tab in this note to access the hot fix for this issue.

Apply the SAS Forecast Server and SAS Time Series Studio hot fixes that are applicable to your release. The hot fix adds the Permissions attribute to all JAR files from which the attribute was previously missing.

Be sure to follow the corresponding post-installation Hot Fix instructions, using the SAS® Deployment Manager to rebuild and re-deploy the SAS Forecast Server and SAS Time Series Studio web applications.

Finally, you must clear the Java Web Start cache in order to reload the SAS Forecast Studio and the SAS Time Series Studio Java Web Start clients. To clear the cache, follow these steps:

  1. Open the Java Control Panel by selecting Start ► Control Panel. In the Control Panel, double-click the Java icon.

    Java icon selected

  2. On the General tab in the Java Control Panel dialog box, click the Settings button, as shown below.

    image label

  3. In the Temporary Files Settings dialog box, click the Delete Files button.

    image label

  4. In the Delete Files and Applications dialog box, select all three check boxes. Then click OK.

    image label

  5. Reload the SAS Forecast Server and SAS Time Series Studio Java Web Start clients again from their Status web pages.


Operating System and Release Information

Product FamilyProductSystemProduct ReleaseSAS Release
ReportedFixed*ReportedFixed*
SAS SystemSAS Forecast ServerMicrosoft® Windows® for x6412.113.29.3 TS1M29.4 TS1M2
Microsoft Windows 8 Enterprise 32-bit12.113.29.3 TS1M29.4 TS1M2
Microsoft Windows 8 Enterprise x6412.113.29.3 TS1M29.4 TS1M2
Microsoft Windows 8 Pro 32-bit12.113.29.3 TS1M29.4 TS1M2
Microsoft Windows 8 Pro x6412.113.29.3 TS1M29.4 TS1M2
Microsoft Windows 8.1 Enterprise 32-bit12.113.29.3 TS1M29.4 TS1M2
Microsoft Windows 8.1 Enterprise x6412.113.29.3 TS1M29.4 TS1M2
Microsoft Windows 8.1 Pro12.113.29.3 TS1M29.4 TS1M2
Microsoft Windows 8.1 Pro 32-bit12.113.29.3 TS1M29.4 TS1M2
Microsoft Windows Server 2003 Datacenter Edition12.19.3 TS1M2
Microsoft Windows Server 2003 Enterprise Edition12.19.3 TS1M2
Microsoft Windows Server 2003 Standard Edition12.19.3 TS1M2
Microsoft Windows Server 2003 for x6412.19.3 TS1M2
Microsoft Windows Server 200812.113.29.3 TS1M29.4 TS1M2
Microsoft Windows Server 2008 R212.113.29.3 TS1M29.4 TS1M2
Microsoft Windows Server 2008 for x6412.113.29.3 TS1M29.4 TS1M2
Microsoft Windows Server 2012 Datacenter12.113.29.3 TS1M29.4 TS1M2
Microsoft Windows Server 2012 R2 Datacenter12.113.29.3 TS1M29.4 TS1M2
Microsoft Windows Server 2012 R2 Std12.113.29.3 TS1M29.4 TS1M2
Microsoft Windows Server 2012 Std12.113.29.3 TS1M29.4 TS1M2
Microsoft Windows XP Professional12.19.3 TS1M2
Windows 7 Enterprise 32 bit12.113.29.3 TS1M29.4 TS1M2
Windows 7 Enterprise x6412.113.29.3 TS1M29.4 TS1M2
Windows 7 Home Premium 32 bit12.113.29.3 TS1M29.4 TS1M2
Windows 7 Home Premium x6412.113.29.3 TS1M29.4 TS1M2
Windows 7 Professional 32 bit12.113.29.3 TS1M29.4 TS1M2
Windows 7 Professional x6412.113.29.3 TS1M29.4 TS1M2
Windows 7 Ultimate 32 bit12.113.29.3 TS1M29.4 TS1M2
Windows 7 Ultimate x6412.113.29.3 TS1M29.4 TS1M2
Windows Vista12.19.3 TS1M2
Windows Vista for x6412.19.3 TS1M2
64-bit Enabled AIX12.113.29.3 TS1M29.4 TS1M2
64-bit Enabled HP-UX12.113.29.3 TS1M29.4 TS1M2
64-bit Enabled Solaris12.113.29.3 TS1M29.4 TS1M2
HP-UX IPF12.113.29.3 TS1M29.4 TS1M2
Linux12.113.29.3 TS1M29.4 TS1M2
Linux for x6412.113.29.3 TS1M29.4 TS1M2
Solaris for x6412.113.29.3 TS1M29.4 TS1M2
* For software releases that are not yet generally available, the Fixed Release is the software release in which the problem is planned to be fixed.